I created a custom install file with OCT 2013 SP1 (setup /admin) and it is not installing all the office apps.   The install file is set to install every single Office 2013 apps.  Most of them seem to install (Access/PPT/Word./OneNote/Infopath/Excel/etc) but Lync and Skydrive Pro refuse to install.  I have everything set to "run from my computer" but it is still failing.  No errors pop up during the install.

- Office 2013 SP1 Proplus - just downloaded the ISO today.

- Office 2013 32-bit

- Win7 32-bit Enterprise

Any ideas?

I'm having the same issue with Lync in Office 2013 SP1.  If I run setup.exe and just use default settings Lync installs.  If I run setup with an adminfile Lync doesn't install.  All OCT settings are the same as in Office 2013 which does install Lync. 

After selecting Lync in the Features section didn't work I tried installing Lync in "Add installations and run programs" where I install Symantec E-Vault.  Doesn't work either.  Symantec E-Vault installs but not Lync. 

The odd thing is if I go to Programs and Features and change Office 2013, it shows Lync installed.  If I try to reinstall Lync I get the message that the program is already installed.

Searching the computer for Lync.exe comes up empty.

Office 2013 SP1 Proplus

• Edited by zeeperkreeper Wednesday, March 05, 2014 7:33 PM

I wonder if there's a problem with the particular ISO?  The name of the one ISO I downloaded is

SW_DVD5_Office_Professional_Plus_2013w_SP1_W32_English_MLF_X19-35821.ISO

Hash value is:  12ac4e13e69a40488c879d5330eca506

You are not alone,. I am having the same issue.  If you change the install from programs and features, it shows Lync and all the other apps ticked already.  If you go through the wizard it installs it.  It seems something doesn't get read during the silent install. 

I am using the Office 2013 SP1 x86 media on Windows 8.1.

• Edited by Luvern.N Thursday, March 06, 2014 12:31 AM

I was finally able to install Lync with the OCT, but the only way I could do it was to set it to "Installed on First Use".

After the setup finished, the shortcut for Lync was in the Microsoft Office 2013 menu.  Clicking on it installed it almost instantaneously.  OneDrive may function the same way.  We don't use it so I haven't tried.

• Edited by zeeperkreeper Thursday, March 06, 2014 1:00 AM
• Proposed as answer by zeeperkreeper Thursday, March 06, 2014 1:01 AM
• Unproposed as answer by osu9400 Thursday, March 06, 2014 3:17 AM

Unfortunately this doesn't meet my requirements.  I need Lync to auto start when the user turns the PC on for the first time.  I don't want them to have to find Lync to run it.  

Have you installed any other Office 2013 products on the workstation(s) with an MSP created from OCT using the same name? i.e. 2013.msp or whatever?

Unfortunately MS doesn't tell you that you have to rename the MSP file to something different or hack the registry and delete keys and all that funzies.

I  am doing the exact same deployment and that is the way I had to do that, because some VPs ask for OneNote 2013 as a one-off to go along with Lync and SkyDrive Pro (now OneDrive).

Yes, the existing Office 2013 was installed with an MSP from the OCT.  I did rename the MSP, I even created a new one with a new name but the end result is the same.  Which registry keys need to be deleted? 

Before deleting any reg keys, I did also have to change the config XML settings

So when you run the install you call the MSP and the config file -

setep /adminfile my_mspfile.msp /config proplus.ww\config.xml

Best practice is to use the config.xml file and the OptionStateID to add/remove features.

The feature name can be found in it's core product folder (i.e. groover.ww for SkyDrive Pro) and is defined in the setup.xml file within the folder in the option element.

You'll also want to suppress the reboot and remove <!-- and --!> in the lines to be read from the install

<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
<OptionState Id="GrooveFiles2" State="local" Children="force" />
<Setting Id="SETUP_REBOOT" Value="Never" />

• Proposed as answer by reboot3times Thursday, March 06, 2014 8:34 PM
• Unproposed as answer by reboot3times Thursday, March 06, 2014 8:34 PM

This didn't work for my distribution.  The only way I can get Lync to install is to mark it to Install at First Run in the OCT. 

I edited the config.xml with the entry

<OptionState Id="LyncCoreFiles" State="local" Children="force" />

• Proposed as answer by NeoNamE Monday, June 09, 2014 6:44 AM
• Unproposed as answer by NeoNamE Monday, June 09, 2014 6:44 AM

I wasn't clear.  Editing the config.xml and resetting the Lync branch to a normal install, then using command line setup.exe /adminfile <myadminfile.msp> /config proplus.ww\config.xml did not fix the problem. 

I still have to set the branch to 'install at first run'.  I restored the original config.xml and don't call it in my command line.

• Edited by zeeperkreeper Thursday, March 06, 2014 8:56 PM

Look at this snip.  OneDrive/Lync/Visio Viewer are a different color.  These are the apps that won't install.  This can't be a coincidence. Does this mean anything?

I think I am going to wait a week to see if MS fixes this. Makes no sense for the original Office2013pro download to work and have the sp1 version not work.

• Edited by reboot3times Thursday, March 06, 2014 9:51 PM

I confirm that

my iso name - SW_DVD5_Office_Professional_Plus_2013w_SP1_W32_Russian_MLF_X19-35862 and I have the same problem, lync dont installed durning deployment

at this moment I resolve this problem by using files from office 2013 ISO without SP1. I just "integrate" SP1 by copying msp files into "updates" folder

pros - i have admin setup of office 2013 with sp1

cons - double size of installation folder. requires more time to install.

I have no problem with that since network speeds is fast at this days and installation time not very critical to me

(sorry for my English, I dont know it very well)

• Edited by kuzn2012 Friday, March 07, 2014 4:51 AM

Same problem here - noticed this while trying to make an OCT install from the new Lync 2013 SP1 media - so it probably has the same bug.

I also tried to get a full OCT install from the Office 2013 SP1 media and indeed, no Lync or Skydrive.

I hope these get fixed soon! But as already asked, do MS know about this? What is the correct way to notify them about such things?

BTW, I am talking about these medias:

SW_DVD5_Lync_2013w_SP1_32-BIT_X64_English_MLF_X19-35370.ISO

SW_DVD5_Office_Professional_Plus_2013w_SP1_W32_English_MLF_X19-35821.ISO

Check this out -

http://blogs.technet.com/b/office_resource_kit/archive/2010/12/02/office-customization-tool-faq.aspx

It applies to 2013 as well. Look about half way down the page.

I've done an initial install using a custom MSP for only Lync/SkyDrive Pro and then applied another MSP after to install OneNote using the provided method of msiexec /p my_new_msp_for_OneNote.msp

I, am seeing the same issue when packaging Office 2013 SP1 using the ISO downloaded from the VLSC.  Using OCT, OneDrive for Business and Lync will not install.  I was able to make the installation work by not using OCT and converting to just using the config.xml method.

Here's what I did...

1. Deleted the OCT customized MSP file from the updates directory (or just move it out of there and put it somewhere the installer can't see it).
2. Customized the config.xml file inside the proplus.ww directory (included below).
   
3. Run the installation using setup.exe /config proplus.ww\config.xml

This is what my config.xml file looks like...

<Configuration Product="ProPlus">

	<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
	
	<!-- <Logging Type="standard" Path="%temp%" Template="Microsoft Office Professional Plus Setup(*).txt" /> -->

	<!-- <USERNAME Value="Customer" /> -->
	
	<!-- <COMPANYNAME Value="MyCompany" /> -->
	
	<!-- <INSTALLLOCATION Value="%programfiles%\Microsoft Office" /> -->
	
	<!-- <LIS CACHEACTION="CacheOnly" /> -->
	
	<!-- <LIS SOURCELIST="\\server1\share\Office;\\server2\share\Office" /> -->
	
	<!-- <DistributionPoint Location="\\server\share\Office" /> -->
	
	<OptionState Id="ACCESSFiles" State="local" Children="force" />
	<OptionState Id="EXCELFiles" State="local" Children="force" />
	<OptionState Id="XDOCSFiles" State="local" Children="force" />
	<OptionState Id="LyncCoreFiles" State="local" Children="force" />
	<OptionState Id="OneNoteFiles" State="local" Children="force" />
	<OptionState Id="OUTLOOKFiles" State="local" Children="force" />
	<OptionState Id="PPTFiles" State="local" Children="force" />
	<OptionState Id="PubPrimary" State="local" Children="force" />
	<OptionState Id="GrooveFiles2" State="local" Children="force" />
	<OptionState Id="VisioPreviewerFiles" State="local" Children="force" />
	<OptionState Id="WORDFiles" State="local" Children="force" />
	<OptionState Id="SHAREDFiles" State="local" Children="force" />
	<OptionState Id="TOOLSFiles" State="local" Children="force" />
	
	<Setting Id="SETUP_REBOOT" Value="Never" />
	
	<!-- <Command Path="%windir%\system32\msiexec.exe" Args="/i \\server\share\my.msi" QuietArg="/q" ChainPosition="after" Execute="install" /> -->

</Configuration>

• Proposed as answer by Tony Chen CHNMicrosoft contingent staff, Moderator Tuesday, March 25, 2014 1:51 AM

Thanks for the reply. Unfortunately my MSP file is highly customized with registry keys and  settings.  It also runs a VBS script to pin all the icons to the task bar. By the way, that's a grip I have, why can't the OCT pin the icons?

I got mine to work. 
It was failing as described as long as the OCT config file was in the Updates folder.

I changed my distribution command to read two lines instead of only the setup command.

setup.exe /config config.xml

Msiexec.exe /update 2013sp1.msp

• Proposed as answer by Tony Chen CHNMicrosoft contingent staff, Moderator Tuesday, March 25, 2014 1:51 AM

Yes OCT configuration file with office 2013 with SP1

if you run installation manual, it's ok, if use setup.exe /adminfile its" not work for install Lync, One Drive

Big FAIL of Microsoft OFfice

My solution, install Adminfile office 2013 and run /passive KB UPDATE SP1 on my new workstation

lol, pending resolution Microsoft.

 Yes, this will work (running the SP as an update) but my goal is to reduce the deployment size as much as possible.  I have 6000 people to deliver this thing to over the network.

 Yes, this will work (running the SP as an update) but my goal is to reduce the deployment size as much as possible.  I have 6000 people to deliver this thing to over the network.

I pinged the odsupport blog  & sustained engineering blog folks about this thread, but the best way, is for you to log a case with Support.

On the topic of reducing the deployment size, I can't see that it matters, since the fileset for Office-with-SP1 is only different by adding the extracted SP1 files into the RTM fileset. So there should be no difference at all in the file sizes of doing it either way. There would perhaps be a slightly lesser installation duration (time-wise)when doing it as an "integrated" step, but I can't imagine it would be very

I can confirm the issue here. Deploy with office customization wizard MSP file and Lync and Onedrive do not get installed correctly. It all appears to have installed, but does not place the files. And there are no errors or warnings.

Also the file size does matter when deploying. The integrated SP1 media is 759MB. The RTM media is 708MB. The extracted SP1 files are over 600MB.

Obviously the new SP1 integrated media is smaller by about half. Microsoft didn't simply extract the SP1 files into the RTM media when they released the new "with sp1" media.

Because of this bug I had to deploy 1.4 GB instead of 700MB over a WAN. Installation time is also double when post-patching vs having the SP1 bits deployed initially. Even when patching over the RTM media skydrive pro remains labeled as skydrive pro. This makes me question the SP1 release in general, was it tested at all internally?

Microsoft, please refresh the media as soon as possible. This bug is very easy to reproduce.

-Ben

Not a fix but at least publicly acknowledged (for whatever good that is):

http://blogs.technet.com/b/odsupport/archive/2014/03/11/lync-2013-and-onedrive-for-business-are-not-installed-when-installing-office-2013-with-service-pack-1.aspx

No mention at all of an expected fix :<

I can confirm the issue here. Deploy with office customization wizard MSP file and Lync and Onedrive do not get installed correctly. It all appears to have installed, but does not place the files. And there are no errors or warnings.

Also the file size does matter when deploying. The integrated SP1 media is 759MB. The RTM media is 708MB. The extracted SP1 files are over 600MB.

Obviously the new SP1 integrated media is smaller by about half. Microsoft didn't simply extract the SP1 files into the RTM media when they released the new "with sp1" media.

Because of this bug I had to deploy 1.4 GB instead of 700MB over a WAN. Installation time is also double when post-patching vs having the SP1 bits deployed initially. Even when patching over the RTM media skydrive pro remains labeled as skydrive pro. This makes me question the SP1 release in general, was it tested at all internally?

Microsoft, please refresh the media as soon as possible. This bug is very easy to reproduce.

-Ben

@Ben, that's an astute observation. With the release of Office2007, the traditional concept of "slipstreaming" servicepackfiles was "no longer possible" (according to MS), and, when SP1 for Office2010 was released, the files in the \Updates\ folder of the "slipstreamed" ISO were clearly identical to the extracted content of the SP! download.

Has anybody tried making their own "slipstream" fileset yet? (use RTM ISO, extract the SP1 download into the \Updates\ folder)

In my experience with Office2007 and Office2010, having the SP bits sitting in the \Updates\ folder, doesn't seem to shorten then overall time taken to install, and I've always understood that to be because it isn't a "true" slipstreaming approach, it's just chaining MSPfiles. (but I'm happy to be corrected)

I'm also having the same problem with OCT not installing( or at least not showing) Lync and OneDrive. I'm also having the BSOD issue when outlook starts ( one time only, works after restart). We are using SP1... i can move off the MSP file and onto a config.xml if that will fix the lync /onedrive issue, but does anyone have an idea on why the BSOD is happening?

We are targeting windows 7 machines, replacing office 2007, using SCCM 2007 SP2.

Thanks!

David

• Edited by dacoty1 Friday, March 14, 2014 3:44 PM

They now updated this post with two workarounds:

To work around this issue, do one of the following:

1. Use the Updates folder on the original RTM release and the publically available Service Pack 1 MSP files:http://support.microsoft.com/kb/2817430.

For further information on using the Updates folder to install Office updates, refer to the following Microsoft article: Deploying software updates with an initial Office 2013 installation

2. Use the config.xml file to add Lync and OneDrive post install of Office 2013.  To accomplish this, edit the config.xml file to have the following:

<Configuration Product="ProPlus">

               <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
               <OptionState Id="GrooveFiles2" State="local" Children="force" />
               <OptionState Id="LyncCoreFiles" State="local" Children="force" />

</Configuration>

Once the install of Office 2013 with SP1 has completed, run the following command-line:

<path>\setup.exe /config <path>\config.xml

For further information on using the Config.xml file in Office 2013, refer to the following Microsoft Article:Config.xml file reference for Office 2013

They now updated this post with two workarounds:

To work around this issue, do one of the following:

1. Use the Updates folder on the original RTM release and the publically available Service Pack 1 MSP files:http://support.microsoft.com/kb/2817430.

For further information on using the Updates folder to install Office updates, refer to the following Microsoft article: Deploying software updates with an initial Office 2013 installation

2. Use the config.xml file to add Lync and OneDrive post install of Office 2013.  To accomplish this, edit the config.xml file to have the following:

<Configuration Product="ProPlus">

               <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
               <OptionState Id="GrooveFiles2" State="local" Children="force" />
               <OptionState Id="LyncCoreFiles" State="local" Children="force" />

</Configuration>

Once the install of Office 2013 with SP1 has completed, run the following command-line:

<path>\setup.exe /config <path>\config.xml

For further information on using the Config.xml file in Office 2013, refer to the following Microsoft Article:Config.xml file reference for Office 2013

Where did you find this?  Any indication that the product will be fixed so we don't have to use the workaround?

After spending 5 hours of troubleshooting, i'm joining in as well :-) thanks for those who posted previously, I now know I'm not alone :-)

Hope MS provides a FIX soon as the workaround isn't feasable for us, I need to deploy this to 15'000 users and size does matter on our network.

I have just opened a premier case with MS, just to figure out whether we can expect a solution from the product team any time soon. If i get to know something, i'll let you know.

As mentioned, i have opened a case for this with MS Premier support. The outcome is as following:

- Issue is known by the product team

- You're not alone, others have reported this also

- No date provided for a fix, but they are working on it

I'll let you know when i hear more.

As mentioned, i have opened a case for this with MS Premier support. The outcome is as following:

- Issue is known by the product team

- You're not alone, others have reported this also

- No date provided for a fix, but they are working on it

I'll let you know when i hear more.

• Marked as answer by Tony Chen CHNMicrosoft contingent staff, Moderator Thursday, March 27, 2014 5:58 AM
• Unmarked as answer by osu9400 Monday, March 31, 2014 4:10 PM

New publish of OFFICE 2013 WITH SP1 for VISIO/PROJET/OFFICE PRO since 01/04/2014, 

Tested with SW_DVD5_Office_Professional_Plus_2013w_SP1_32-BIT_X64_French_MLF_X19-35905

X86 not ok with OCT - Lync and one drive enterprise not installed

• Edited by ChrisStyle Sunday, April 06, 2014 12:51 PM

So, for the so called workaround, how do you use the msp file with the config.xml? Since some of us can't do the "install on first use", due to lack of admin rights.  I know the command for the xml file is : <path>\setup.exe /config <path>\config.xml, but how do I add the msp to the install without putting it in the update folder?

Thanks,

So, for the so called workaround, how do you use the msp file with the config.xml? Since some of us can't do the "install on first use", due to lack of admin rights.  I know the command for the xml file is : <path>\setup.exe /config <path>\config.xml, but how do I add the msp to the install without putting it in the update folder?

Thanks,

@Tyler Way,
\\server\share\Office15\setup.exe /adminfile \\server\share\MyUpdates\Engineering.msp

http://technet.microsoft.com/en-us/library/cc178956.aspx

The issue has been FIXED!!!

1. Download the admin files from here: http://www.microsoft.com/en-us/download/details.aspx?id=35554

2. Copy the files in the "Admin" to the "Admin" directory your Office 2013 source location. 

3. setup /admin like normal and import your old custom settings file.

• Marked as answer by osu9400 Tuesday, April 29, 2014 9:27 PM

• Proposed as answer by Nathan Lamont Thursday, May 08, 2014 2:48 PM
• Unproposed as answer by Nathan Lamont Thursday, May 08, 2014 2:48 PM

Just adding to the mix as well, this still does not work even with the new admin folder.

We are installing only Lync 2013 with SP1 from the ISO:
SW_DVD5_Lync_2013w_SP1_32-BIT_X64_English_MLF_X19-35370.ISO

Installing using setup.exe with no OCT file works fine

Installing using setup.exe with an OCT .MSP file in Updates folder does NOT work, even after downloading and adding the new /admin folder from the OCT download at http://www.microsoft.com/en-us/download/details.aspx?id=35554

Edit: Discovered that it does work if in the OCT file under "Set feature installation states" you have to explicitly set top level "Microsoft Office" to Run All from my Computer. If there's no [F], or if you leave that entire branch as default, it does not work.

• Edited by Mike2784 Friday, May 02, 2014 10:45 PM
• Proposed as answer by squishmike Monday, May 05, 2014 8:24 PM

This still doesn't work.  I've tried replacing the entire admin folder, specifying "Run All From My Computer", and it fails.  Now, whenever I open the .MSP file and attempt to specify "Run All From My Computer" and hit "save file", the file errors out and gives me this:

Unhandled exception:

NodeType get property called for OXmlNode with Null interface

The file fails to even save.

The fix for this is a little bit different:

1) Download the new admin files from here: http://www.microsoft.com/en-us/download/details.aspx?id=35554

2) Unzip the file.  Copy the entire "Admin" folder over top of your existing "Admin" folder within your setup files

3) Run the setup.exe /admin and create a NEW MSP file

4) Make sure to specify "Run All From My Computer" under the "Set feature installation states" section.

It's important to note that if you do NOT create the new MSP file, this will fail.  If you create a new MSP file, Lync should install.

• Proposed as answer by Courtney Culver Monday, May 05, 2014 5:22 PM

The fix for this is a little bit different:

1) Download the new admin files from here: http://www.microsoft.com/en-us/download/details.aspx?id=35554

2) Unzip the file.  Copy the entire "Admin" folder over top of your existing "Admin" folder within your setup files

3) Run the setup.exe /admin and create a NEW MSP file

4) Make sure to specify "Run All From My Computer" under the "Set feature installation states" section.

It's important to note that if you do NOT create the new MSP file, this will fail.  If you create a new MSP file, Lync should install.

I think it's important to note as well that it needs to be a NEW .MSP file regardless if you're using an .MSP file made from the new /admin folder or not.

If you create an .MSP file with the new /admin folder downloaded, and for whatever reason forget to check "Run All From My Computer", you can't go back into that previously saved .MSP file and check it, as the same issue will occur (Lync doesn't install). For whatever reason, it needs to be a fresh MSP file every time.

I found this out the hard way as I created a new package that worked, but then went back into the MSP as I needed to change something, and to my surprise, it was back to not installing Lync. Not until I created a new MSP again did I realize this... /sigh Microsoft...

• Edited by squishmike Tuesday, May 06, 2014 6:16 PM

Ok well now it's starting to seem random whether it works or not.

I've only been able to make one .MSP file that actually installed Lync. Every time I try to make changes to it, or if I create a new MSP, Lync simply doesn't install. Incredibly frustrating.

Is Microsoft going to fix this issue or what? It's also rather misleading that an answer has been "accepted" when it's not actually fixed.

• Edited by squishmike Tuesday, May 06, 2014 6:16 PM

I am also still experiencing this issue.

But I was able to play with my setup to make it work. (Using Office 2013 Pro-Plus 32-bit)

To deploy via SCCM 2012 R2 I took different parts of advice from this thread, mainly:

> Download the new admin pack from http://www.microsoft.com/en-us/download/details.aspx?id=35554

> Download, extract and replace your admin folder with the admin folder inside the extracted bunch

> In the root of your office setup in cmd run setup.exe /admin to bring up OCT.

> In the "Set feature installation states" part of the OCT configure the Top Level "Microsoft Office" to "Run all from My Computer" (Everything will go bold, and have a [F] in front of the product name)

> Config the stuff you don't want available; in this case I didn't want OneDrive and InfoPath, so I made those not available.

> Save your msp to the 'updates' folder in the root of your office folder. I recommend a unique name too your other attempts and it being the only file in the folder.

I then went to the "proplus.ww" folder and edited config.xml. I specifically started at the "Setting ID" and added the following to the file.

	<Setting Id="SETUP_REBOOT" Value="Never" />

	<INSTALLLOCATION Value="" />
	<OptionState Id="ACCESSFiles" State="Local" Children="force" />
	<OptionState Id="EXCELFiles" State="Local" Children="force" />
	<OptionState Id="XDOCSFiles" State="Absent" Children="force" />
	<OptionState Id="LyncCoreFiles" State="Local" Children="force" />
	<OptionState Id="OneNoteFiles" State="Local" Children="force" />
	<OptionState Id="OUTLOOKFiles" State="Local" Children="force" />
	<OptionState Id="PPTFiles" State="Local" Children="force" />
	<OptionState Id="PubPrimary" State="Local" Children="force" />
	<OptionState Id="GrooveFiles2" State="Absent" Children="force" />
	<OptionState Id="VisioPreviewerFiles" State="Local" Children="force" />
	<OptionState Id="WORDFiles" State="Local" Children="force" />
	<OptionState Id="SHAREDFiles" State="Local" Children="force" />
	<OptionState Id="TOOLSFiles" State="Local" Children="force" />

I think the important part is the <INSTALLATIONLOCATION VALUE="" /> and below.

As you can see above I changed the state of GrooveFiles2 to Absent (I believe this is Onedrive) and XDOCSFiles (InfoPath).

> I then set the Program Installation in SCCM to the following 

setup.exe /config proplus.ww\config.xml

With all that, I was able to deploy exactly what I wanted from Office 2013 INCLUDING Lync 2013.

Good luck.

Nathan Lamont

• Edited by Nathan Lamont Thursday, May 08, 2014 11:14 PM
• Proposed as answer by Fazal M Khan Wednesday, June 18, 2014 4:19 PM

I am also still experiencing this issue.

But I was able to play with my setup to make it work. (Using Office 2013 Pro-Plus 32-bit)

To deploy via SCCM 2012 R2 I took different parts of advice from this thread, mainly:

> Download the new admin pack from http://www.microsoft.com/en-us/download/details.aspx?id=35554

> Download, extract and replace your admin folder with the admin folder inside the extracted bunch

> In the root of your office setup in cmd run setup.exe /admin to bring up OCT.

> In the "Set feature installation states" part of the OCT configure the Top Level "Microsoft Office" to "Run all from My Computer" (Everything will go bold, and have a [F] in front of the product name)

> Config the stuff you don't want available; in this case I didn't want OneDrive and InfoPath, so I made those not available.

> Save your msp to the 'updates' folder in the root of your office folder. I recommend a unique name too your other attempts and it being the only file in the folder.

I then went to the "proplus.ww" folder and edited config.xml. I specifically started at the "Setting ID" and added the following to the file.

	<Setting Id="SETUP_REBOOT" Value="Never" />

	<INSTALLLOCATION Value="" />
	<OptionState Id="ACCESSFiles" State="Local" Children="force" />
	<OptionState Id="EXCELFiles" State="Local" Children="force" />
	<OptionState Id="XDOCSFiles" State="Absent" Children="force" />
	<OptionState Id="LyncCoreFiles" State="Local" Children="force" />
	<OptionState Id="OneNoteFiles" State="Local" Children="force" />
	<OptionState Id="OUTLOOKFiles" State="Local" Children="force" />
	<OptionState Id="PPTFiles" State="Local" Children="force" />
	<OptionState Id="PubPrimary" State="Local" Children="force" />
	<OptionState Id="GrooveFiles2" State="Absent" Children="force" />
	<OptionState Id="VisioPreviewerFiles" State="Local" Children="force" />
	<OptionState Id="WORDFiles" State="Local" Children="force" />
	<OptionState Id="SHAREDFiles" State="Local" Children="force" />
	<OptionState Id="TOOLSFiles" State="Local" Children="force" />

I think the important part is the <INSTALLATIONLOCATION VALUE="" /> and below.

As you can see above I changed the state of GrooveFiles2 to Absent (I believe this is Onedrive) and XDOCSFiles (InfoPath).

With all that, I was able to deploy exactly what I wanted from Office 2013 INCLUDING Lync 2013.

Good luck, and let me know how it goes.

Nathan Lamont

Sorry, I should of added completely slipped my mind I will edit my post.

My Installation program is set to

setup.exe /config proplus.ww\config.xml

Haven't tried just pointing at the setup alone.

I'm kind of happy it's working as it is.

Nathan Lamont

I am also still experiencing this issue.

But I was able to play with my setup to make it work. (Using Office 2013 Pro-Plus 32-bit)

To deploy via SCCM 2012 R2 I took different parts of advice from this thread, mainly:

> Download the new admin pack from http://www.microsoft.com/en-us/download/details.aspx?id=35554

> Download, extract and replace your admin folder with the admin folder inside the extracted bunch

> In the root of your office setup in cmd run setup.exe /admin to bring up OCT.

> In the "Set feature installation states" part of the OCT configure the Top Level "Microsoft Office" to "Run all from My Computer" (Everything will go bold, and have a [F] in front of the product name)

> Config the stuff you don't want available; in this case I didn't want OneDrive and InfoPath, so I made those not available.

> Save your msp to the 'updates' folder in the root of your office folder. I recommend a unique name too your other attempts and it being the only file in the folder.

I then went to the "proplus.ww" folder and edited config.xml. I specifically started at the "Setting ID" and added the following to the file.

	<Setting Id="SETUP_REBOOT" Value="Never" />

	<INSTALLLOCATION Value="" />
	<OptionState Id="ACCESSFiles" State="Local" Children="force" />
	<OptionState Id="EXCELFiles" State="Local" Children="force" />
	<OptionState Id="XDOCSFiles" State="Absent" Children="force" />
	<OptionState Id="LyncCoreFiles" State="Local" Children="force" />
	<OptionState Id="OneNoteFiles" State="Local" Children="force" />
	<OptionState Id="OUTLOOKFiles" State="Local" Children="force" />
	<OptionState Id="PPTFiles" State="Local" Children="force" />
	<OptionState Id="PubPrimary" State="Local" Children="force" />
	<OptionState Id="GrooveFiles2" State="Absent" Children="force" />
	<OptionState Id="VisioPreviewerFiles" State="Local" Children="force" />
	<OptionState Id="WORDFiles" State="Local" Children="force" />
	<OptionState Id="SHAREDFiles" State="Local" Children="force" />
	<OptionState Id="TOOLSFiles" State="Local" Children="force" />

I think the important part is the <INSTALLATIONLOCATION VALUE="" /> and below.

As you can see above I changed the state of GrooveFiles2 to Absent (I believe this is Onedrive) and XDOCSFiles (InfoPath).

> I then set the Program Installation in SCCM to the following 

setup.exe /config proplus.ww\config.xml

With all that, I was able to deploy exactly what I wanted from Office 2013 INCLUDING Lync 2013.

I understand that it is using the config.xml method of customisation and the OCT - But it's better than nothing.

Nathan Lamont

• Edited by Nathan Lamont Monday, May 12, 2014 9:36 AM

All-

The release notes state that you need a new MSP or you must IMPORT your existing.  Simply copying the old one over will not work.

Yea, even with a NEW MSP file it still doesn't work.

I was able to make it work however using the setup.exe in /admin mode outside of the x86 or x64 folders. This is for the Lync 2013 standalone install.

The ISO extracts both an x86 and x64 folder each containing their own setup.exe and admin folders. I replaced the admin folder as suggested earlier in this thread in the x86 folder, then used the setup.exe that was in the root (up one level from x86) to create the .MSP. Then if I mark everything to Run all from Computer, it works.

MS Lync 2013 x64 wSP1 itself cannot be installed with OCT way.

This can lead to raise issue or bug on Lync 2013 SP1 binaries not compatible with OCT technology.

Thanks Nathan. It really worked for me. Much appreciated for your solution. 

Regards,

Fazal

The fix for this is a little bit different:

1) Download the new admin files from here: http://www.microsoft.com/en-us/download/details.aspx?id=35554

2) Unzip the file.  Copy the entire "Admin" folder over top of your existing "Admin" folder within your setup files

3) Run the setup.exe /admin and create a NEW MSP file

4) Make sure to specify "Run All From My Computer" under the "Set feature installation states" section.

It's important to note that if you do NOT create the new MSP file, this will fail.  If you create a new MSP file, Lync should install.

Thanks this worked for me.  I was able to put the OCT MSP file into the Updates folder and it install all Office products.

I don't know if you've already stumbled across this but it's a known issue with the VLSC SP1 slipstreamed installer. There's a KB article for it, you do need to do all steps. I created the custom MSP with the upgraded admin components but it still didn't install Lync or OneDrive.

http://support.microsoft.com/kb/2973210

I had the same problem...

Turns out that there is a NEW Office Customization Tool (the ISO downloaded from the Volume Licensing Service Centre has a BUG in the OCT)

Read this BLOG it explains it in MUCH more detail... basically just download the new OCT extract the new files, open your existing customization and resave it. (SCCM users... don't forget to update your source afterwards)

http://blogs.technet.com/b/odsupport/archive/2014/03/21/lync-2013-and-onedrive-for-business-are-not-installed-when-installing-office-2013-with-service-pack-1.aspx